Provides a space for you to type the interval between screen refreshes (in seconds).


Provides a space for you to type the user name for this network connection.


Provides a space for you to type the password for this network connection.


Specifies that your local computer is added as a server.


Specifies that a remote computer is added as a server.


Provides a space for you to type the computer name or IP address (in dotted decimal notation) of the remote computer.


Specifies that Windows 2000 Active Directory is searched for the computer to add as a server.


Specifies that all computers running Routing and Remote Access from a specified domain are added as servers.


Provides a space for you to type the domain name that contains the computers running Routing and Remote Access.


Specifies whether Windows 2000 Active Directory is searched for LAN routers. A LAN router does not support demand-dial or virtual private network (VPN) routing.


Specifies whether Windows 2000 Active Directory is searched for LAN and demand-dial routers.


Specifies whether Windows 2000 Active Directory is searched for remote access servers.


Lists the attributes of routers and remote access servers stored in Windows 2000 Active Directory. Select the attributes you want to search for.


Clears all selected attributes for routers and remote access servers.


Selects all attributes for routers and remote access servers.


Specifies whether this computer is enabled as a router. A router can forward network packets from one network segment to another.


Specifies that this computer is a LAN-only router and does not require demand-dial or virtual private network (VPN) connections.


Specifies that this computer is a LAN and demand-dial router and supports virtual private network (VPN) connections.


Specifies whether this computer is enabled as a remote access server, which supports either dial-up or virtual private network (VPN) connections.


Click to configure the authentication methods supported by this server for remote access and demand-dial connections.


Specifies whether the server allows unauthenticated connections. Unauthenticated connections do not require a user name or password. For more information, see Unauthenticated access in Routing and Remote Access Help.


Specifies whether the server uses the Extensible Authentication Protocol (EAP) to authenticate remote access and demand-dial connections. To view the installed EAP methods, click Details. For more information, see EAP in Routing and Remote Access Help.


Click to view the installed EAP methods.


Specifies whether the server uses Microsoft Challenge Handshake Authentication Protocol (MS-CHAP) version 2 to authenticate remote access and demand-dial connections. MS-CHAP v2 provides mutual authentication and stronger encryption and is required for encrypted Point-to-Point (PPP) or Point-to-Point Tunneling Protocol (PPTP) connections. For more information, see MS-CHAP version 2 in Routing and Remote Access Help.


Specifies whether the server uses the Microsoft Challenge Handshake Authentication Protocol (MS-CHAP) to authenticate remote access and demand-dial connections. MS-CHAP is required for encrypted Point-to-Point (PPP) or Point-to-Point Tunneling Protocol (PPTP) connections. For more information, see MS-CHAP in Routing and Remote Access Help.


Specifies whether the server uses the Message Digest 5 (MD-5) Challenge Handshake Authentication Protocol (CHAP) to authenticate remote access and demand-dial connections. For more information, see CHAP in Routing and Remote Access Help.


Specifies whether the server uses the Shiva Password Authentication Protocol (SPAP) to authenticate remote access and demand-dial connections. For more information, see SPAP in Routing and Remote Access Help.


Specifies whether the server uses the Password Authentication Protocol (PAP) to authenticate remote access and demand-dial connections. During a PAP authentication, passwords are sent in plaintext, or unencrypted, form. You should use this authentication protocol only when support for non-Microsoft PAP remote access clients is required. For more information, see PAP in Routing and Remote Access Help.


Lists the available authentication providers for remote access or demand-dial authentication.

Windows Authentication: The server uses a Windows 2000 local, Windows 2000 domain, or Windows NT 4.0 domain account database to authenticate remote access or demand-dial connection credentials. The server logs connection authentication information in log files that are configured in the properties of the Remote Access Logging folder.

RADIUS Authentication: The remote access server uses a Remote Authentication Dial-In User Service (RADIUS) server to authenticate remote access or demand-dial connection credentials.


Click to configure the selected authentication provider.


Lists the available accounting providers for remote access or demand-dial connections.

Windows Accounting: The server logs connection accounting information in log files that are configured in the properties of the Remote Access Logging folder.

RADIUS Accounting: The server sends connection accounting information to a Remote Authentication Dial-In User Service (RADIUS) server.


Click to configure the selected accounting provider.


Specifies whether IP routing—the forwarding of IP packets from one routing interface to another—is enabled on this server. You must enable IP routing in order for LAN and demand-dial routing to occur. If you want IP-based remote access clients to access the entire network to which this server is attached, enable IP routing. If you want IP-based remote access clients to access this server only, disable IP routing.


Specifies whether the Internet Protocol Control Protocol (IPCP) is negotiated for Point-to-Point Protocol (PPP) connections, which allows IP-based remote access and demand-dial connections.


Specifies that the server uses DHCP to obtain IP addresses assigned to TCP/IP-based remote access and demand-dial connections.


Specifies that the server uses a configured static pool of IP addresses for allocation to TCP/IP-based remote access and demand-dial connections. For more information about configuring static IP address pools, see TCP/IP and remote access in Routing and Remote Access Help.


Provides a space for you to type an Internet Protocol (IP) address that corresponds to the range of IP address in the static pool. For more information about configuring static IP address pools, see TCP/IP and remote access in Routing and Remote Access Help.


Provides a space for you to type the mask that corresponds to the range of IP addresses in the static pool. For more information about configuring static IP address pools, see TCP/IP and remote access in Routing and Remote Access Help.


Displays the calculated range of IP addresses in the static pool based on the values in Address and Mask. The first possible IP address in the range is not shown because it is reserved for the server. For more information about configuring static IP address pools, see TCP/IP and remote access in Routing and Remote Access Help.


Displays the calculated number of IP addresses in the static pool based on the values in Address and Mask. The number of addresses does not include the first IP address in the range, which is reserved for the server. For more information about configuring static IP address pools, see TCP/IP and remote access in Routing and Remote Access Help.


Lists the available adapters. The selected adapter is used to obtain the IP addresses for allocation (if configured to use DHCP) and the IP addresses of DNS and WINS servers for assignment to remote access clients and demand-dial routers. By default, Allow RAS to select adapter is selected, which means that the server randomly selects an adapter when the Routing and Remote Access service is started.


Select the method to assign IP addresses to remote access clients and demand-dial routers.


Lists the ranges of addresses that correspond to the static IP address pool for the server.


Click to add an address range to the list.


Click to modify a selected address range in the list.


Removes a selected address range from the list.


Provides a space for you to type the starting IP address (in dotted decimal notation) for the address range.


Provides a space for you to type the ending IP address (in dotted decimal notation) for the address range.


Provides a space for you to type the number of IP addresses in the range.


Specifies whether the Internetwork Packet Exchange Control Protocol (IPXCP) is negotiated for Point-to-Point Protocol (PPP) connections, which allows IPX-based remote access and demand-dial connections.


Specifies that the server automatically allocates IPX network numbers to remote access clients and demand-dial routers.


Specifies that the server uses a configured range of IPX network numbers for allocation to remote access clients and demand-dial routers.


Provides a space for you to type the first IPX network number in the range.


Provides a space for you to type the last IPX network number in the range.


Specifies whether the server assigns the same IPX network number to all IPX-based remote access clients and demand-dial routers.


Specifies whether the remote access server allows IPX node numbers to be requested by remote access clients and demand-dial routers during the connection establishment process.


Specifies whether the NetBIOS Frames Control Protocol (NBFCP) is negotiated for Point-to-Point Protocol (PPP) connections, which allows NetBEUI-based remote access connections.


Specifies that remote access clients can only access the resources of the server.


Specifies that remote access clients can access the resources of the server and the resources of the network to which the server is attached.


Specifies whether the AppleTalk Control Protocol (ATCP) is used to negotiate Point-to-Point Protocol (PPP) remote access connections.


Specifies whether the server uses the PPP Multilink Protocol (MP), which allows remote access clients and demand-dial routers to combine multiple physical connections into a single logical connection.


Specifies whether the server uses the Bandwidth Allocation Protocol (BAP) and Bandwidth Allocation Control Protocol (BACP) to negotiate the dynamic addition or deletion of multiple physical connections for remote access clients and demand-dial routers.


Specifies whether the server uses Link Control Protocol (LCP) extensions. Clearing this check box prevents LCP from sending Time-Remaining and Identification packets and requesting callback during LCP negotiation. For more information, see Remote access RFCs in Routing and Remote Access Help and RFC 1570, "PPP LCP Extensions."


Specifies whether the server uses the Microsoft Point-to-Point Compression Protocol (MPPC) to compress data sent on the remote access or demand-dial connection.


Specifies that no events are logged in the System Log in Event Viewer.


Specifies that only errors are logged in the System Log in Event Viewer.


Specifies that errors and warnings are logged in the System Log in Event Viewer.


Specifies that the maximum amount of information is logged in the System Log in Event Viewer.


Specifies whether the events in the Point-to-Point Protocol (PPP) connection establishment process for remote access and demand-dial routing connections are written to the Ppp.log file stored in the systemroot\Tracing folder (the default location). For more information about tracing, see Using tracing in Routing and Remote Access Help. You must restart the Routing and Remote Access service for changes to this setting to take effect.


Lists the RADIUS servers that are configured. To add a new RADIUS server, click Add. To change the properties of a RADIUS server, click the RADIUS server you want to modify, and then click Edit. To remove a RADIUS server from the list, click the server you want to remove, and then click Remove.


Click to add a new RADIUS server to the list.


Click to modify the properties of the selected RADIUS server.


Removes the selected RADIUS server from the list.


Provides a space for you to type the DNS name or IP address of the Remote Authentication Dial-In User Service (RADIUS) server. IP addresses must be typed in dotted decimal notation.


Displays the obscured shared secret that is used for secure communications between the remote access server and the RADIUS server. You must configure the same shared secret on both the remote access server and the RADIUS server for successful RADIUS communications to occur. The shared secret is case-sensitive.


Click to change the shared secret.


Provides a space for you to type the amount of time (in seconds) that the remote access server tries to obtain responses from the RADIUS server before trying another RADIUS server. You can also click the arrows to select a new setting.


Provides a space for you to type the initial responsiveness score of the RADIUS server. You can also click the arrows to select a new setting. The score increases or decreases based on the ongoing responsiveness of the RADIUS server.


For RADIUS Authentication:

Provides a space for you to type the UDP port that is used by the RADIUS server for incoming RADIUS authentication requests. The default value of 1812 is based on RFC 2138. For older RADIUS servers, set the port value to 1645.

For RADIUS Accounting:

Provides a space for you to type the UDP port that is used by the RADIUS server for incoming RADIUS accounting messages. The default value of 1813 is based on RFC 2139. For older RADIUS servers, set the port to 1646.


For RADIUS Authentication:

Provides a space for you to type the UDP port that is used by the RADIUS server for incoming RADIUS authentication requests. The default value of 1812 is based on RFC 2138. For older RADIUS servers, set the port value to 1645.

For RADIUS Accounting:

Provides a space for you to type the UDP port that is used by the RADIUS server for incoming RADIUS accounting messages. The default value of 1813 is based on RFC 2139. For older RADIUS servers, set the port to 1646.


Specifies whether RADIUS Accounting-On and Accounting-Off messages are sent to the RADIUS server when the Routing and Remote Access service starts up and shuts down. You should verify that the RADIUS server supports these messages before selecting this check box.


Specifies whether a digital signature based on the shared secret is sent with each RADIUS message. Extensible Authentication Protocol (EAP) messages are always sent with a digital signature. Make sure that your RADIUS servers are capable of and configured to receive digital signatures.

You must select this option if your RADIUS server is a Windows 2000 computer running Internet Authentication Service (IAS) and the RADIUS client that is configured for this server has the Client must always send the signature attribute in the request option selected.


Provides a space for you to type the current shared secret. The shared secret is case-sensitive.


Provides a space for you to type the new shared secret. You must configure the same shared secret on both the remote access server and the RADIUS server for successful RADIUS communications to occur. The shared secret is case-sensitive.


Provides a space for you to type the new shared secret to confirm the change. The shared secret is case-sensitive.


Lists the available EAP methods that are installed on this server. You can configure an EAP method on the Authentication tab in the profile properties of a remote access policy. The Smart Card or other Certificate EAP type is not available on a stand-alone remote access server.


Provides a space for you to type the user name to use when dialing in to a remote router. The user name must match the name of a user account on the remote router that has dial-in permissions.

For two-way initiated demand-dial connections, the user name must also match the name of a demand-dial interface on the remote router. For example, if the remote router has a demand-dial interface with the name BranchOffice, then the remote router must also create a user with the name BranchOffice with dial-in permissions. In this example, the user name is BranchOffice.


Provides a space for you to type the name of the domain for the user account that has been created on the remote router. If no domain is specified, then the domain of the remote router is assumed.


Provides a space for you to type the password to use when dialing in to the remote router. This is the password for the user account created on the remote router.


Provides a space for you to type the password again to confirm that you typed the password correctly.


Provides a space for you to type the name of the interface for this IP tunnel.


Specifies that a demand-dial connection is initiated only when IP packets forwarded over this demand-dial interface match one of the filters listed. When the demand-dial interface is in a disconnected state, all packets forwarded by using the demand-dial interface are compared to the filters listed. If a packet matches a filter, the demand-dial connection is initiated and the packet is forwarded across the demand-dial connection. If the packet does not match a filter, the demand-dial connection is not initiated and the packet is discarded.

This option applies to all the filters that you have added. You cannot change this option for individual filters.

You can only configure this option after you have added at least one filter.


Specifies that a demand-dial connection is not initiated for IP packets forwarded over this demand-dial interface that match one of the filters listed. When the demand-dial interface is in a disconnected state, all packets forwarded by using the demand-dial interface are compared to the filters listed. If the packet matches a filter, the demand-dial connection is not initiated and the packet is discarded. If a packet does not match a filter, the demand-dial connection is initiated and the packet is forwarded across the demand-dial connection.

This option applies to all the filters that you have added. You cannot change this option for individual filters.

You can only configure this option after you have added at least one filter.


Displays the recipient of the message.


Provides a space for you to type the contents of the message.


Lists the installed devices on the server, which includes dial-up equipment (such as modems) and tunneling protocols (PPTP and L2TP) for virtual private network connections. To configure a device, click the device, and then click Configure.


Click to configure the selected device.


Specifies whether inbound remote access connections are allowed for the ports of this device.


Specifies whether inbound or outbound demand-dial connections are allowed for the ports of this device.


Provides a space for you to type the phone number of this device. The phone number is used as the Called Station ID and in Bandwidth Allocation Protocol (BAP)-enabled connections. When a BAP-enabled remote access client requests another connection, the remote access server sends back a message that contains the phone number to dial for the new connection.

For the Called Station ID, you need to manually configure the called number if:

1. 	You are using the Called-Station-Id attribute in a remote access policy.

2. 	Your phone line, dial-up hardware, and driver for your dial-up hardware do not support the identification of the called number.

The number typed here must match the number typed in the Called-Station-Id attribute of the remote access policy. Otherwise, the connection is rejected. If your phone line, dial-up hardware, and driver for your dial-up hardware do support the identification of the called number, then the number typed here is ignored.

For L2TP or PPTP ports, the number you type here is the IP address (in dotted decimal notation) that is assigned to the interface of the VPN server on which VPN connections are received.


Provides a space for you to type the maximum number of ports for this device. You can also click the arrows to select a new setting. You can only configure this option on devices that support a variable number of ports.


Displays the maximum number of ports on this device.


Lists the installed ports.


Refreshes the display of port statistics and port errors.


Sets all port statistics and port errors to zero.


Ends the active connection on the selected port.


Lists the active remote access connections.


Refreshes the display of connection statistics and connection errors.


Sets all connection statistics and connection errors to zero.


Ends the selected remote access connection.


Specifies whether this router is used to assign AppleTalk network numbers to AppleTalk computers on the network segment that is connected to this interface.


Provides a space for you to type the starting network number in the range of AppleTalk network numbers being seeded on this interface.


Provides a space for you to type the ending network number in the range of AppleTalk network numbers being seeded on this interface.


Select the zone that is the default zone.


Displays the current default zone.


Lists the zones on this interface.


Provides a space for you to type a new zone for nodes on this interface. To add the new zone to the list of zones, click Add.


Click to add a zone to the list of zones for this interface.


Removes the selected zone from the list of zones for this interface.


Obtains a list of zones for nodes on this interface from other AppleTalk routers on this network segment.


Makes the selected zone the default zone for nodes on this interface.


Zones are groups of AppleTalk nodes on different network segments. You can add zones, remove zones, and make a specific zone the default zone.


The range of networks typed here are used to seed network numbers on this interface.


Specifies that no events are logged in the System Log in Event Viewer.


Specifies that only errors are logged in the System Log in Event Viewer.


Specifies that errors and warnings are logged in the System Log in Event Viewer.


Specifies that the maximum amount of information is logged in the System Log in Event Viewer.


Lists the preference level of the route sources. If two routes exist to the same destination, then the route learned by the route source with a smaller rank number is preferred over the route learned by the route source with a higher rank number regardless of the route metric. For example, if Open Shortest Path First (OSPF) is at a higher preference level than RIP Version 2 for Internet Protocol, then an OSPF route with a metric of 5 is entered into the routing table rather than the same route discovered by RIP with a metric of 3.


Raises the preference level for a selected route source by lowering its rank number.


Lowers the preference level for a selected route source by raising its rank number.


Lists the configured multicast scopes. A multicast scope is a named range of IP multicast addresses that is expressed with an IP address and mask. Once multicast scopes are configured, you can use them to create scope-based multicast boundaries in the properties of an IP routing interface.


Click to add a multicast scope.


Click to modify the selected multicast scope.


Removes the selected multicast scope.


Provides a space for you to type the name of the scope to use when configuring multicast boundaries. A scope is a range of multicast IP addresses.


Provides a space for you to type the IP address for the administrative multicast scope (in dotted decimal notation). Valid administrative, nonlocal, multicast scopes must be in the range 239.0.0.0 through 239.254.255.255. For more information, see Expressing an IP address range with a mask in Routing and Remote Access Help.


Provides a space for you to type the mask for the scope (in dotted decimal notation). For more information, see Expressing an IP address range with a mask in Routing and Remote Access Help.


Specifies whether TCP/IP is enabled on this interface. Select this check box to set the Administrative Status of the interface to Up. Clear this check box to set the Administrative Status of the interface to Down.


Specifies whether Internet Control Message Protocol (ICMP) router discovery advertisements are enabled over this interface. Router discovery clients use these messages to dynamically configure their default gateways. Windows 2000 implements router discovery by using multicast ICMP router advertisement messages.


Provides a space for you to type the preference level of using this interface as the default gateway. A higher number means that this gateway is more preferred by router discovery clients as the default gateway. You can also click the arrows to select a new setting.


Provides a space for you to type the minimum number of minutes between router discovery advertisement packets. The default is 7 minutes. You can also click the arrows to select a new setting. The router advertisement is sent at a random interval between the minimum time and the maximum time.


Provides a space for you to type the maximum number of minutes between router discovery advertisement packets. The default is 10 minutes. You can also click the arrows to select a new setting. The router advertisement is sent at a random interval between the minimum time and the maximum time.


Provides a space for you to type the number of minutes that a router discovery advertisement from this router and this interface is valid. The default is 30 minutes. You can also click the arrows to select a new setting.


Click to apply packet filters to incoming packets on this interface.


Click to apply packet filters to outgoing packets on this interface.


Specifies whether the router discards all fragmented IP packets that it receives on this interface. This option only applies to incoming traffic. To prevent the router from forwarding fragmented IP packets on any interface, select this check box on all interfaces of the router.


Provides a space for you to type the IP address of the local endpoint of the IP-in-IP tunnel. Type an IP address that is assigned to an interface of the router.


Provides a space for you to type the IP address of the remote endpoint of the IP-in-IP tunnel. Type an IP address that is assigned to an interface of the router on the other end of the tunnel.


Provides a space for you to type the value of the Time-to-Live (TTL) field in the outer IP header for packets sent through this IP-in-IP tunnel. The TTL is the maximum number of links on which the IP datagram can travel before being discarded by an IP router. The default is 5. The TTL value should be large enough to traverse the IP internetwork between this router and the tunnel endpoint. You can also click the arrows to select a new setting.


For input filters: Specifies that all incoming packets that match the filters listed are discarded. All incoming packets are compared to the filters listed. If a packet matches a filter, the packet is dropped. If the packet does not match a filter, the packet is accepted.

For output filters: Specifies that all outgoing packets that match the filters listed are discarded. All outgoing packets are compared to the filters listed. If a packet matches a filter, the packet is dropped. If the packet does not match a filter, the packet is transmitted.

This option applies to all the filters that you have added. You cannot change this option for individual filters.

You can only configure this option after you have added at least one filter.


For input filters: Specifies that all incoming packets that match the filters listed are accepted. All incoming packets are compared to the filters listed. If a packet matches a filter, the packet is accepted. If the packet does not match a filter, the packet is dropped.

For output filters: Specifies that all outgoing packets that match the filters listed are transmitted. All outgoing packets are compared to the filters listed. If a packet matches a filter, the packet is transmitted. If the packet does not match a filter, the packet is dropped.

This option applies to all the filters that you have added. You cannot change this option for individual filters.

You can only configure this option after you have added at least one filter.


Lists all the configured filters.


Click to add a filter. You can set filters based on where the packet is coming from (the source), where the packet is going (the destination), or what protocol the packet is using. You can set all three of these values for a filter or set any one or combination of the three, depending on the level of control that you want.


Click to modify the settings for a selected filter.


Removes a selected filter from the list.


Specifies whether the filter checks the network from which the packet is coming. After selecting this check box, you must specify a network IP address and subnet mask.


Provides a space for you to type the IP address of the network from which the packet was sent. You must also specify a subnet mask.


Provides a space for you to type the subnet mask that corresponds to the network IP address in IP Address.


Specifies whether the filter checks the network to which the packet is going. After selecting this check box, you must specify a network address and subnet mask.


Provides a space for you to type the IP address of the network to which the packet is going. You must also specify a subnet mask.


Provides a space for you to type the subnet mask that corresponds to the network IP address in IP Address.


Lists the available protocol types that you can base a filter on. The default is Any protocol. If you select Other, you must type a protocol identifier in Protocol number.


For TCP, TCP (established), and UDP protocols, provides a space for you to type the port number specified by the source to be used by the filter. Some applications use well-known ports to send and receive packets. You can set a filter for one of these ports if you know what numbers the application uses for the protocol specified in Protocol. For example, you can try to block FTP traffic or allow only PPTP traffic.

For the ICMP protocol, provides a space for you to type the ICMP type.

For the Other protocol, provides a space for you to type the IP protocol number.


For TCP, TCP (established), and UDP protocols, provides a space for you to type the port number used by the destination for the packet.

For the ICMP protocol, provides a space for you to type the ICMP code.


Specifies that this network connection dynamically obtains an Internet Protocol (IP) address from a Dynamic Host Configuration Protocol (DHCP) server.


Specifies that this network connection uses a manually specified Internet Protocol (IP) address. If you click this option, you must specify an IP address and a subnet mask.


Provides a space for you to type an Internet Protocol (IP) address obtained from your network administrator or Internet service provider. An IP address is a 32-bit number notated by using four numbers from 0 through 255, separated by periods.


Provides a space for you to type the subnet mask number obtained from your network administrator or Internet service provider. This number is used with the IP address number to identify which network your computer is on.

A subnet mask is a 32-bit number notated by using four numbers from 0 through 255, separated by periods. Typically, default subnet mask numbers use either 0 or 255 as values (such as 255.255.255.0), but you can use other number values; they indicate that subnetting of a single TCP/IP network is in use.


Provides a space for you to type the IP address for the default gateway you want to add. This is the address of a local IP router on the same network as this computer, which is used to route and forward traffic between destinations beyond the local network. The value in each field must be a number from 0 through 255.

A gateway is the connection or interchange point that connects separate IP networks. For example, a local area network (LAN) may need a gateway to connect it to a wide area network (WAN) or to the Internet.


Click to configure advanced IP addressing properties for this network connection, such as multiple IP addresses or multiple default gateways.


Lists additional IP addresses and subnet masks that can be assigned to this network connection. This setting is useful if this computer connects to a single physical network but requires advanced IP addressing because of either of the following reasons:

•	A single logical IP network is in use and this computer needs to use more than one IP address to communicate on that network.

•	Multiple logical IP networks are in use and this computer needs a different IP address to communicate with each of the different logical IP networks.


Click to add an additional IP address and subnet mask for use with this interface.


Click to modify a selected IP address (or its related subnet mask) that is configured for this interface.


Removes a selected IP address that is configured for this interface.


Lists additional default gateways that can be used by this interface. A default gateway is a local IP router that is used to reach destinations beyond the local network.


Click to add the IP address for an additional default gateway used by this interface.


Click to modify the IP address for a selected additional default gateway used by this interface.


Removes the IP address for a selected additional default gateway used by this interface.


Provides a space for you to type the interface metric for this interface. The metric indicates the cost of using the routes that are associated with this interface and becomes the value in the Metric column for those routes in the IP routing table. If there are multiple routes to a destination in the IP routing table, the route with the lowest metric is used. The default value is 1.


Provides a space for you to type an additional IP address that this network connection can use. After you type the address, in Subnet Mask, type the subnet mask number that is used with this address.


Provides a space for you to type the subnet mask number that is used with the address specified in IP Address.


Provides a space for you to type the IP address for an additional default gateway that this network connection can use.


Provides a space for you to type the metric for the default gateway. The metric is used to indicate the cost of using the default gateway and becomes the Metric value for the default route in the IP routing table. The default route has the Network Destination set to 0.0.0.0 and the Netmask set to 0.0.0.0. If there are multiple default routes in the IP routing table, the default route with the lowest metric is used. The default value is 1.


Specifies whether the router performs group scoping to prevent the forwarding of IP multicast traffic as identified by the multicast group IP address.


Lists the available multicast scopes that are configured on the Multicast Scopes tab in the properties of IP Routing-General. A multicast scope is a named range of IP multicast addresses that is defined by an IP address and mask.


Lists the scopes for the multicast traffic that will not be forwarded out this interface.


Click to add the selected scope to the list of scopes.


Removes the selected multicast scope from the list.


Specifies whether the router performs Time-to-Live (TTL) scoping to prevent the forwarding of IP multicast traffic out this interface with a TTL less than a specified value. TTL scoping applies to all multicast packets regardless of the multicast group.


Provides a space for you to type the maximum TTL for multicast traffic that is forwarded out this interface. You can also click the arrows to select a new setting.


Provides a space for you to type the maximum rate (in kilobytes per second) for all multicast traffic forwarded by this interface.


Specifies whether the router listens for a regular multicast notification that is sent to a configured IP multicast group address to verify that IP multicast connectivity is available on the network. Multicast heartbeat listens for a periodic multicast announcement to a specific group address. If the announcement is not received by the quiet time, the Windows 2000 router sets the multicast heartbeat status on the configured interface to inactive. The multicast heartbeat status for the interface can be polled by a program to provide notification that the multicast heartbeat is no longer present. For more information, see the Windows 2000 Software Development Kit.


Provides a space for you to type the IP address (in dotted decimal notation) of the multicast group.


Provides a space for you to type the number of minutes the router waits before setting the multicast heartbeat status on the interface to inactive. You can also click the arrows to select a new setting.


Provides a space for you to type a destination for the route. The destination can be a host address, subnet address, network address, or the destination for the default route (0.0.0.0).


Provides a space for you to type the network mask for the static route. The network mask number is used in conjunction with the destination to determine when the route is used. For example, a host route has a mask of 255.255.255.255, a default route has a mask of 0.0.0.0, and a subnet or network route has a mask somewhere in between these two extremes. The mask of 255.255.255.255 means that only an exact match of the destination number can use this route. The mask of 0.0.0.0 means that any destination can use this route.

When converted to binary, the destination cannot have bits set to 1 where there are 0’s in the network mask. In other words, the destination cannot be more specific that the network mask.


Provides a space for you to type the forwarding IP address for this route. For LAN interfaces, the gateway address must be configured and must be a directly reachable IP address for the network segment of the selected interface. For demand-dial interfaces, the gateway address is not configured or used.


Provides a space for you to type the metric, which is the cost associated with this route to reach the destination. The metric is commonly used to indicate the number of routers (hops) to the destination. When deciding between multiple routes to the same destination, the route with the lowest metric is selected as the best route. You can also click the arrows to select a new setting.


Lists the available LAN or demand-dial interfaces to be used to forward the IP packet if this route is selected.


Specifies whether the router initiates a demand-dial connection when this route is selected for packets being forwarded. This check box is only available when a demand-dial interface is selected in Interface.


Provides a space for you to type the route source preference level for this static route. The route source preference level defines the preference of this route source when compared with other route sources such as routing protocols. A lower route source preference number is preferred over a higher preference number. A route source preference of 1 is the most preferred level. You can also click the arrows to select a new setting.

You can view the preference levels of your route sources on the Preference Levels tab (in the properties of the General node under IP Routing).


Lists the available views for which this route is available. There are separate unicast and multicast forwarding processes that use the routes in the routing table to make forwarding decisions.

•	If the route should be viewed by both unicast and multicast forwarding processes, click Both. This is the default.

•	If the route should be viewed by just the unicast forwarding process, click Unicast.

•	If the route should be viewed by just the multicast forwarding process, click Multicast.


Lists the IP addresses of DHCP servers on the network. The router acts as a DHCP relay agent by relaying DHCP messages between DHCP clients and the DHCP servers specified in this list. You must add at least one address to be a relay agent.

For the DHCP relay agent to work, you must select the Relay DHCP packets check box on at least one interface that has been added to the DHCP Relay Agent routing protocol.


Adds the IP address specified in Server address to the list of DHCP servers.


Removes a selected DHCP server address from the list.


Provides a space for you to type the IP address of the DHCP server you want to add.


Specifies whether DHCP messages are relayed between DHCP clients on the subnet to which this interface is attached and DHCP servers.

After you select this check box, you must configure the DHCP server addresses in the DHCP Relay Agent Properties dialog box.


Provides a space for you to type a value for the maximum number of DHCP relay agents that will handle DHCP relayed traffic. You can also click the arrows to select a new setting. The default value is 4 hops. The maximum value is 16 hops.


Provides a space for you to type the number of seconds the relay agent waits before forwarding DHCP messages. You can also click the arrows to select a new setting. The default value is 4 seconds.

This option is useful when you want a local DHCP server to respond first, but if the local DHCP server does not respond, you want to forward messages to a remote DHCP server.


Provides a space for you to type the interval between triggered updates. You can also click the arrows to select a new setting. Triggered updates are sent when the entries in a routing table change. The default is 5 seconds.


Specifies that no events are logged in the System Log in Event Viewer.


Specifies that only errors are logged in the System Log in Event Viewer.


Specifies that errors and warnings are logged in the System Log in Event Viewer.


Specifies that the maximum amount of information is logged in the System Log in Event Viewer.


Specifies that announcements from all routers are accepted. This is the default.


Specifies that only announcements from the routers listed are accepted. Any announcements from routers that are not on the list are ignored. This option is useful if you want to accept RIP announcements only from specific RIP routers.


Specifies that announcements from the routers listed are ignored. Announcements from all other routers are accepted. This option is useful if you want to exclude the announcements of specific RIP routers.


Lists the IP addresses of the RIP routers that you have added.


Adds the router IP address specified in Router IP address to the list.


Removes the selected router IP address.


Provides a space for you to type the IP address of the router.


Lists the available operation modes. You can select one of two operation modes: auto-static update mode or periodic update mode.

Auto-static update mode sends out RIP announcements only when other routers request an update. Routes learned over RIP while in auto-static mode are marked as static routes when they are stored in the routing table. If you start and stop the router or if RIP is disabled, these routes remain in the routing table until they are manually deleted.

Auto-static update mode is the default for demand-dial interfaces.

Periodic update mode sends out RIP announcements periodically, as specified in Periodic announcement interval on the Advanced tab. Routes learned over RIP while in periodic mode are marked as RIP routes and are removed if the router is stopped and restarted.

Periodic update mode is the default for LAN interfaces.


Lists the available protocols for outgoing RIP announcements. You can use the following protocols to send route announcements over the interface:

RIP version 1 broadcast: RIP version 1 announcements are sent as broadcasts.

RIP version 2 broadcast: RIP version 2 announcements are sent as broadcasts. If you have a mixed environment with RIP versions 1 and 2, select this protocol.

RIP version 2 multicast: RIP version 2 announcements are sent as multicasts. Select this protocol only if all the neighboring RIP routers on the network that is connected to this interface are also RIP version 2 routers that are configured for RIP version 2. A RIP version 1 router cannot process a RIP version 2 multicast announcement.

Silent RIP: Disables outgoing RIP announcements on this interface. In silent mode, the computer listens to RIP announcements and updates its routing table but does not announce its own routes.


Lists the available protocols for incoming RIP announcements. You can use the following protocols to receive RIP packets from other routers:

Ignore incoming packets: Ignores announcements. If you want a router that only announces routes, select this option.

RIP version 1 and 2: Accepts announcements of both types.

RIP version 1 only: Accepts only RIP version 1 announcements.

RIP version 2 only: Accepts only RIP version 2 announcements.


Provides a space for you to type the cost associated with sending packets over this interface. You can also click the arrows to select a new setting. When routes are added to the routing table, this number is added to the hop count as advertised in the RIP message. By default, this value is 1 to indicate the additional hop as created by the receiving router. If you want to associate a higher cost with the route, set a higher cost (for example, if you have a heavily trafficked route that you do not want used unless other routes are unavailable). The accumulated costs/hops for the farthest nodes on the IP internetwork must not exceed 15.


Provides a space for you to type a tag number for the routes advertised on this interface. You should use this option if you want all packets sent over this interface to include a tag in RIP version 2 announcements.


Specifies whether you want to enable authentication by using a plaintext password for RIP version 2 announcements over this interface. All incoming and outgoing RIP version 2 packets must contain the same plaintext password. Therefore, you must enable this option and configure the same password for all routers that are connected to this interface. This option is a form of identification. It is not a security option.


Provides a space for you to type a password between 1 and 16 characters long. This password is sent as plaintext in the RIP version 2 message for authentication between neighboring RIP version 2 routers.


Specifies that all RIP announcements are sent by using the outgoing packet protocol specified on the General tab.


Specifies that RIP announcements are unicasted to specific neighboring routers in addition to the outgoing packet protocol specified on the General tab.


Specifies that RIP announcements are only unicasted to the specified neighboring routers. RIP announcements are not sent according to the outgoing packet protocol specified on the General tab. If you have nonbroadcast networks such as Frame Relay and want to enable RIP between specific routers, you should select this option.


Lists the configured RIP neighbor IP addresses.


Adds the IP address of the neighboring router specified in IP address to the list.


Removes a selected IP address from the list.


Replaces a selected IP address in the list with the IP address typed in IP address.


Provides a space for you to type the IP address of the neighboring RIP router.


Lists the available security options for RIP for IP. You can set security for how you accept routes and how you announce routes. All of the options on this tab are specific to the security option you selected. To set security for accepting routes, click For incoming routes and configure the security options. Then, to set security for announcing routes, click For outgoing routes and reconfigure the security options.


For incoming routes:

Specifies that the router looks at every route entry in an incoming RIP announcement to determine whether to update its routing table.

For outgoing routes:

Specifies that the router includes all appropriate route entries in outgoing RIP announcements.


For incoming routes:

Specifies that the router looks at each route entry in an incoming RIP announcement and processes the route only if the route falls between one of the ranges listed.

For outgoing routes:

Specifies that the router includes a route in the outgoing RIP announcement only if the route falls into one of the ranges listed.


For incoming routes:

Specifies that the router looks at each route entry in an incoming RIP announcement and discards the route if it falls into one of the ranges listed.

For outgoing routes:

Specifies that the router excludes a route from the outgoing RIP announcement if the route falls into one of the ranges listed.


For incoming routes:

Lists the route ranges to filter in the incoming RIP announcements.

For outgoing routes:

Lists the route ranges to filter in the outgoing RIP announcements.


Adds the IP address range specified in From and To to the list.


Replaces a selected IP address range in the list with the IP address range typed in From and To.


Removes a selected IP address range from the list.


Provides a space for you to type the IP address for the lower end of the range. For example, if you want to exclude all routes to the private network ID 10.0.0.0, you type 10.0.0.0 in From.


Provides a space for you to type the IP address for the higher end of the range. For example, if you want to exclude all routes to the private network ID 10.0.0.0, you type 10.255.255.255 in To.


Provides a space for you to type the number of seconds between periodic RIP announcements. You can also click the arrows to select a new setting. The default value is 30 seconds. You can set this value from 15 seconds through 86,400 seconds (24 hours). This option is valid only if you have selected Periodic update mode as the Operation mode on the General tab.


Provides a space for you to type the lifetime (in seconds) of a route that is learned through RIP. You can also click the arrows to select a new setting. The default value is 180 seconds. You can set this value from 15 seconds through 259,200 seconds (72 hours). If a route is not updated with another RIP announcement within the time set, the route expires and is marked as an invalid route. This option is valid only if you have selected Periodic update mode as the Operation mode on the General tab.


Provides a space for you to type the amount of time (in seconds) after which a RIP-learned route that has expired is removed from the routing table. You can also click the arrows to select a new setting. The default value is 120 seconds. You can set this value from 15 seconds through 259,200 seconds (72 hours). This option is valid only if you have selected Periodic update mode as the Operation mode on the General tab.


Specifies whether routes learned on a network are not announced in RIP announcements sent on that network. If this check box is not selected, routes learned on a network are announced on the same network. By default, split horizon is enabled.


Specifies whether routes learned on a network are announced with a metric of 16 (unreachable) in RIP announcements sent on that network. By default, poison reverse is enabled. The poison-reverse option is available only after split horizon is enabled.


Specifies whether new routes and metric changes trigger an immediate update that includes only the changes. This is called a triggered update. The maximum time between triggered updates depends on the value of Minimum seconds between triggered updates, which you set on the General tab in the RIP dialog box.


Specifies whether, if RIP is stopping on this interface, RIP sends an announcement with all routes that are marked with a metric of 15. This enables neighboring routers to immediately update their routing tables to indicate that the routes available through the router that is stopping are no longer reachable. If this check box is selected, when the router is stopped, the router advertises all of the routes that it makes available as being unreachable on all of its interfaces. By default, this check box is enabled.


Specifies whether host routes in received RIP announcements are accepted. By default, host routes are ignored.


Specifies whether host routes are included in RIP announcements. By default, host routes are not included.


Specifies whether default routes in received RIP announcements are accepted. By default, default routes are ignored.


Specifies whether default routes are included in RIP announcements. By default, default routes are not included.


Specifies that subnet routes are not summarized in the form of the class-based network ID when announced on a network that is not a subnet of the class-based network ID. By default, subnet summarization is disabled. This option is only available if the Outgoing packet protocol on the General tab is set to either RIP version 2 broadcast or RIP version 2 multicast.


Specifies whether the Internet Group Management Protocol (IGMP) is enabled for multicast forwarding on this interface. IGMP is used by hosts to register membership in IP multicast groups. Enabling IGMP on this interface allows the router to either listen for IGMP messages sent by hosts or forward IGMP messages received on other interfaces.


Specifies that IGMP router mode is enabled on this interface. An interface in IGMP router mode listens for IGMP messages from hosts and updates the TCP/IP multicast forwarding table.


Specifies that IGMP proxy mode is enabled on this interface. An interface in IGMP proxy mode acts as a host, forwarding IGMP host membership messages for all IGMP host membership messages received on all other interfaces on which IGMP router mode is enabled. Additionally, all nonlocal multicast traffic received on all other interfaces (on which IGMP router mode is enabled) is forwarded over the IGMP proxy mode interface.


Lists the version of IGMP supported on this interface (IGMP version 1 or IGMP version 2).


You can configure this interface to run in one of two modes: IGMP router mode or IGMP proxy mode.


You can configure this interface to support either IGMP version 1 or IGMP version 2.


Provides a space for you to type the robustness variable. The robustness variable is a way of indicating the lossy nature of the subnet to which this interface is attached. IGMP can recover from lost IGMP packets(robustness variable is set to 1). You can also click the arrows to select a new setting. You should set the robustness variable to a value of 2 or greater. The default robustness variable is 2. For more information, see Routing RFCs in Routing and Remote Access Help and RFC 2236, "Internet Group Management Protocol, Version 2."


Provides a space for you to type the query interval. The query interval is the amount of time in seconds between IGMP General Query messages sent by the router (if the router is the querier on this subnet). You can also click the arrows to select a new setting. The default query interval is 125 seconds. For more information, see Routing RFCs in Routing and Remote Access Help and RFC 2236, "Internet Group Management Protocol, Version 2."


Provides a space for you to type the query response interval. The query response interval is the maximum amount of time in seconds that the IGMP router waits to receive a response to a General Query message. You can also click the arrows to select a new setting. The default query response interval is 10 seconds and must be less than the query interval. For more information, see Routing RFCs in Routing and Remote Access Help and RFC 2236, "Internet Group Management Protocol, Version 2."


Provides a space for you to type the last member query interval. The last member query interval is the amount of time in milliseconds that the IGMP router waits to receive a response to a Group-Specific Query message. The last member query interval is also the amount of time in seconds between successive Group-Specific Query messages. You can also click the arrows to select a new setting. The default last member query interval is 1 second. For more information, see Routing RFCs in Routing and Remote Access Help and RFC 2236, "Internet Group Management Protocol, Version 2."


IGMP variables can be manually configured or automatically calculated based on the values of the robustness variable and the query interval. For automatic calculation, select the Enable automatic recalculation of defaults check box.


Provides a space for you to type the startup query interval. The startup query interval is the amount of time in seconds between successive General Query messages sent by a querier during startup. You can also click the arrows to select a new setting. The default startup query interval is ¼ of the query interval. For more information, see Routing RFCs in Routing and Remote Access Help and RFC 2236, "Internet Group Management Protocol, Version 2."


Provides a space for you to type the startup query count. The startup query count is the number of general query messages sent at startup. You can also click the arrows to select a new setting. The default startup query count is 2. For more information, see Routing RFCs in Routing and Remote Access Help and RFC 2236, "Internet Group Management Protocol, Version 2."


Provides a space for you to type the last member query count. The last member query count is the number of Group-Specific Query messages sent before the router assumes there are no members of the host group being queried on this interface. You can also click the arrows to select a new setting. The default last member query count is 2. For more information, see Routing RFCs in Routing and Remote Access Help and RFC 2236, "Internet Group Management Protocol, Version 2."


Specifies whether the values in Startup query interval, Startup query count, and Last member query count are calculated automatically based on the following:

•	The startup query interval is ¼ of the value for the query interval.

•	The startup query count is the same value as the robustness variable.

•	The last member query count is the same value as the robustness variable.


Displays the calculated group membership interval. The group membership interval is the number of seconds that must pass before a multicast router determines that there are no more members of a host group on a subnet. The group membership interval is (robustness variable) * (query interval) + (query response interval). For more information, see Routing RFCs in Routing and Remote Access Help and RFC 2236, "Internet Group Management Protocol, Version 2."


Displays the calculated other querier present interval. The other querier present interval is the number of seconds that must pass before a multicast router determines that there is no other multicast router that should be the querier. The other querier present interval is (robustness variable) * (query interval) + (query response interval)/2. For more information, see Routing RFCs in Routing and Remote Access Help and RFC 2236, "Internet Group Management Protocol, Version 2."


Provides a space for you to type the 32-bit number (in dotted decimal notation) that uniquely identifies an OSPF router in the network. One way to make sure the number is unique is to select the largest or the smallest IP address assigned to one of the interfaces on the computer. You can use the ipconfig command to see a list of the IP addresses for the interfaces.


Specifies whether the router acts as an Autonomous System (AS) boundary router. An AS boundary router advertises external routing information from other route sources, such as static routes and the Routing Information Protocol (RIP), into the OSPF AS. AS boundary routers can be internal or area border routers and can be connected to the backbone.


Specifies that no OSPF events are logged in Event Viewer.


Specifies that only OSPF errors are logged in Event Viewer.


Specifies that OSPF errors and warnings are logged in Event Viewer.


Specifies that the maximum amount of OSPF information is logged in Event Viewer.


Lists the OSPF areas for this router. You can use OSPF areas as a way of subdividing the network. A router can have many areas. Each OSPF interface on the router must belong to one area.

To use the OSPF routing protocol, you must configure at least one area. If you configure more than one area, you must also configure a backbone area. The area number of 0.0.0.0 is reserved for the backbone area. You can configure a total of 16 areas.


Click to add a new OSPF area.


Click to modify settings for the selected OSPF area.


Removes the selected OSPF area.


Provides a space for you to type an ID for the area. This is a 32-bit number expressed in dotted decimal notation that identifies the OSPF area. The area ID does not need to coincide with an IP address or IP network ID. The area ID of 0.0.0.0 is reserved for the backbone. If the area represents a subnetted network, you can use the IP network number of the subnetted network for the area ID.


Specifies whether plaintext passwords are required for the area. If you require passwords for an area:

•	All interfaces in the same area that are on the same network segment must use identical passwords.

•	Interfaces in the same area that are on different networks can have different passwords.

By default, passwords are enabled and the password is 12345678. Passwords are transmitted in plaintext, so this option is for identification, not security.


Specifies whether this area is configured as a stub area. A stub area is an OSPF area that does not enumerate external routes. External routes from outside the OSPF Autonomous System (AS) are not flooded into or through stub areas. Routing to AS external destinations in these areas is based only on a summary default route. This reduces the overhead for a stub area's internal routers.

You cannot configure the backbone as a stub area. You cannot configure virtual links through stub areas.


Provides a space for you to type the cost of the summary default route that the router advertises into the stub area. If the area is configured as a stub area, and the router itself is an area border router, then the stub metric indicates the cost of the summary default route that the router advertises into the area.


Specifies whether inter-area routes for the OSPF autonomous system are imported into this stub area. By default, this check box is disabled; therefore, all non-intra-area destinations are routed based on a single default route.


Lists the IP address and mask pair that define a range of addresses belonging to this area. OSPF ranges are used to summarize the routes within this OSPF area.


Adds the range specified in Destination and Network mask to the list.


Removes the selected range from the list.


Provides a space to you to type the destination for the range.


Provides a space to you to type the network mask for the range.


Lists the virtual interfaces for this router. A virtual interface is used to create a virtual link. A virtual link is a logical connection between a backbone area border router and an area border router that cannot be physically connected to the backbone area. Once created, the virtual link is used to exchange routing information between the area border router of the noncontiguous area and the backbone area border router.


Click to add a virtual interface to this router. Because you cannot configure a virtual interface across the backbone area (area 0.0.0.0), you can only add a virtual interface if there are nonbackbone areas configured on this router.


Click to modify the selected virtual interface.


Removes the selected virtual interface.


Lists the nonbackbone area IDs configured on this router.


Provides a space for you to type the OSPF router ID of the router at the other end of the virtual link.


Provides a space for you to type the estimated number of seconds that it takes to transmit OSPF packets to the virtual link neighbor router over this interface. You can also click the arrows to select a new setting.


Provides a space for you to type the number of seconds between link state advertisement retransmissions. You can also click the arrows to select a new setting. This number should be significantly larger than the expected round-trip delay between any two routers on the attached network. Because this can be difficult to estimate for a virtual link, it is better to make this number too large rather than too small.


Provides a space for you to type the length of time, in seconds, between hello packets that are sent out on this interface. The two virtual interfaces that make up a virtual link must use the same value for the hello interval. You can also click the arrows to select a new setting.


Provides a space for you to type the number of seconds a router's neighbors will wait after they cease to hear the router's hello packets before they declare that the router is down. The two virtual interfaces that make up a virtual link must use the same value for the dead interval. You can also click the arrows to select a new setting.


Provides a space for you to type the plaintext password for the virtual interface. The two virtual interfaces that make up a virtual link must have the same password.


Specifies that routes from all the selected route sources are ignored.


Specifies that routes from all the selected route sources are accepted.


Lists the non-OSPF route sources for external route information.


Click to set filters for external routes.


Specifies whether all the listed external routes are ignored.


Specifies whether all the listed external routes are accepted.


Lists the external routes that are either ignored or accepted.


Adds the external route specified in Destination and Network mask to the list.


Removes a selected external route from the list.


Provides a space for you to type the destination for the external route you want to add.


Provides a space for you to type a network mask for the external route you want to add.


Lists the IP addresses assigned to this interface. This list is only available when multiple IP addresses are assigned to this interface. All OSPF settings on the General, NBMA Neighbors, and Advanced tabs pertain to the IP address that you selected. If multiple IP addresses are configured for this interface, you must select and then configure OSPF settings for each IP address.


Lists the IP addresses assigned to this interface. This list is only available when multiple IP addresses are assigned to this interface. All OSPF settings on the General, NBMA Neighbors, and Advanced tabs pertain to the IP address that you selected. If multiple IP addresses are configured for this interface, you must select and then configure OSPF settings for each IP address.


Lists the IP addresses assigned to this interface. This list is only available when multiple IP addresses are assigned to this interface. All OSPF settings on the General, NBMA Neighbors, and Advanced tabs pertain to the IP address that you selected. If multiple IP addresses are configured for this interface, you must select and then configure OSPF settings for each IP address.


Specifies whether OSPF is enabled on the interface for the selected IP address.


Lists the available areas for the interface. An interface can belong in only one area. If you have multiple IP addresses, you can select a different area for each IP address.


Provides a space for you to type OSPF router priority for this interface. You can also click the arrows to select a new setting. Larger numbers indicate a higher priority. When two routers attached to a network both attempt to become the designated router, the router with the highest router priority setting takes precedence. If there is still a tie, the router with the highest router ID value takes precedence.

However, when you set up a new router interface, if a designated router exists, the new router defers to the existing designated router, regardless of the priority value you configure for the new interface. If the interface has a priority value of 0, it cannot become the designated router. The priority setting is ignored for point-to-point links.


Provides a space for you to type the cost of sending a packet out of this interface. You can also click the arrows to select a new setting. Cost indicates ranking and is determined by the administrator of the network. The term metric is often used synonymously with cost. The value set here is advertised as the link cost for this interface in the link state advertisement of the router.

The lower the cost, the more often the interface is used. Faster interfaces usually have lower costs. The maximum setting is 32,767.


If passwords are enabled for the area (the default setting), provides a space for you to type the password used for this interface by using any combination of uppercase or lowercase letters or numbers.

•	All interfaces in the same area that are on the same network must use identical passwords.

•	Interfaces in the same area that are on different networks can have different passwords.

By default, passwords are enabled and the password is 12345678. Passwords are transmitted in plaintext, so this option is for identification, not security. If this option is unavailable, you must enable passwords for the area.


Specifies that this interface is a broadcast OSPF interface. OSPF then works as a multiple access broadcast network; that is, multiple routers can be connected to the network. Broadcast networks can address a single frame to all the attached routers. Broadcast network types are Ethernet, Token Ring, and FDDI.


Specifies that this interface is a point-to-point OSPF interface. A point-to-point configuration is a connection between a single pair of routers. Examples of point-to-point network types are T1/E1, T3/E3, ISDN, and other types of dial-up links.


Specifies that this interface is a non-broadcast multiple access (NBMA) OSPF interface. Examples of NBMA network types are X.25, Frame Relay, and Asynchronous Transfer Mode (ATM). If you specify this type of interface, you can configure neighboring routers by using the NBMA Neighbors tab.


Lists the neighboring routers that are attached to the nonbroadcast network and their priorities. Each router is listed by its IP interface address on the network. Also, for each router listed, the eligibility of that router to become a designated router must be defined. When an interface to a nonbroadcast network comes up, the router sends hello packets only to those neighbors eligible to become a designated router until the identity of the designated router is discovered. A neighbor is eligible to become the designated router if its router priority is 1 or greater.

The options on this tab are only available if the Non-broadcast multiple access (NBMA) network type is selected on the General tab.


Adds the neighbor IP address and its priority specified in Neighboring IP address and Router priority to the list.

The options on this tab are only available if the Non-broadcast multiple access (NBMA) network type is selected on the General tab.


Removes a selected neighbor IP address and its priority from the list.

The options on this tab are only available if the Non-broadcast multiple access (NBMA) network type is selected on the General tab.


Provides a space for you to type the IP address of the neighbor that you want to add. The IP address is the IP interface address of the neighbor router on the NBMA network. This is not the OSPF router ID of the neighbor.

The options on this tab are only available if the Non-broadcast multiple access (NBMA) network type is selected on the General tab.


Provides a space for you to type the OSPF router priority of the neighbor. You can also click the arrows to select a new setting. For each router listed, the eligibility of that router to become a designated router must be defined. When an interface to a nonbroadcast network comes up, the router sends hello packets only to those neighbors eligible to become a designated router until the identity of the designated router is discovered. A neighbor is eligible to become the designated router if its router priority is 1 or greater.

The options on this tab are only available if the Non-broadcast multiple access (NBMA) network type is selected on the General tab.


Provides a space for you to type the estimated number of seconds it takes to transmit a link state update packet over this interface. You can also click the arrows to select a new setting. This value should take into account the transmission and propagation delays of the interface and network media. The default setting is 1 second.


Provides a space for you to type the number of seconds between link state advertisement retransmissions for adjacencies belonging to this interface. You can also click the arrows to select a new setting. This value should exceed the expected round-trip delay between any two routers on the attached network. However, if this value is not conservative, needless retransmissions result. The value needs to be larger on low-speed serial lines. A sample value for a local area network is 5 seconds.


Provides a space for you to type the interval in seconds between transmissions of hello packets by the router on the interface. You can also click the arrows to select a new setting. This setting must be the same for all routers that are attached to a common network. The shorter the hello interval, the faster topological changes are detected. However, a shorter interval also results in more OSPF traffic. A sample value for an X.25 network is 30 seconds. A sample value for a local area network is 10 seconds.


Provides a space for you to type the number of seconds before a neighboring router considers this router to be down. You can also click the arrows to select a new setting. The router is determined to be down if a neighboring router does not receive a hello packet sent by this router within the specified interval. For example, if your hello interval setting is 15 seconds and your dead interval is 60 seconds, after sending four hello packets and receiving no acknowledgment or response, neighboring routers declare that this router is down. This setting should be an integral multiple of the hello interval (commonly 4). This value must be the same for all OSPF router interfaces attached to a common network segment.


Provides a space for you to type the number of seconds between OSPF network polls for non-broadcast multiple access (NBMA) interfaces only. You can also click the arrows to select a new setting. If a neighboring router is down (hello packets have not been sent for the number of seconds determined by the dead interval setting), it might still be necessary to send hello packets to the dead neighbor in order to determine if the connection has been restored. This is called the poll interval. You should set the poll interval to be at least twice as long as the dead interval. A sample value for an X.25 network is 2 minutes.


Provides a space for you to type the maximum size in bytes of IP packets carrying OSPF information. You can also click the arrows to select a new setting.

The maximum transmission unit (MTU) size is the maximum size of an IP datagram that can be sent without fragmentation. The default value of 1,500 bytes is the default IP MTU for an Ethernet network. The maximum packet size on a 100-MB FDDI ring network is 4,352 bytes. The size can be much smaller on a radio channel.


Specifies that no events are logged in the System Log in Event Viewer.


Specifies that only errors are logged in the System Log in Event Viewer.


Specifies that errors and warnings are logged in the System Log in Event Viewer.


Specifies that the maximum amount of information is logged in the System Log in Event Viewer.


Provides a space for you to type the number of minutes that a dynamic mapping for a TCP session remains in the translation table for the router. You can also click the arrows to select a new setting. The default value for TCP sessions is 1,440 minutes (24 hours).


Provides a space for you to type the number of minutes that a dynamic mapping for a UDP message remains in the translation table for the router. You can also click the arrows to select a new setting. The default value for UDP messages is 1 minute.


Sets the time-out values for dynamic mappings for TCP traffic to 1,440 minutes (24 hours) and UDP traffic to 1 minute.


Click to configure special applications running on the private network that you want to make available to users on the Internet. Applications that you need to configure are those that send response traffic from a different port than the port used by the initial incoming traffic from the Internet client.


Specifies whether the router provides DHCP-based address assignment to DHCP clients on the private network.


Provides a space for you to type an Internet Protocol (IP) address that corresponds to the range of addresses to be assigned to DHCP clients on the private network. The network you configure here should be a private network or a subnet of a private network. The private networks are 10.0.0.0 with a subnet mask of 255.0.0.0, 172.16.0.0 with a subnet mask of 255.240.0.0, and 192.168.0.0 with a subnet mask of 255.255.0.0. The default IP network is 192.168.0.0.


Provides a space for you to type the subnet mask that corresponds to the range of addresses to be assigned to hosts on the private network. The default subnet mask is 255.255.255.0.


Click to disable address assignment on specified interfaces. You should enable address assignment on the interfaces that are connected to the private network.


Click to specify any addresses within the configured range of addresses that should not be assigned to DHCP clients on the private network because they are already in use.


Lists the addresses that are excluded from the configured address range. IP addresses in this list are not allocated to DHCP clients on the private network.


Click to add an IP address to the list of reserved addresses.


Click to modify the selected IP address in the list of reserved addresses.


Removes the selected IP address from the list of reserved addresses.


Provides a space for you to type the reserved IP address (in dotted decimal notation).


Specifies whether the router relays Windows Internet Name Service (WINS) name resolution requests from hosts on the private network to the configured WINS server for the router.


Specifies whether the router relays Domain Name System (DNS) name resolution requests from hosts on the private network to the configured DNS server for the router.


Click to disable name resolution on specific interfaces. You should enable name resolution on the interfaces that are connected to the private network.


Lists the demand-dial interfaces that are configured on the router.


Specifies whether a connection is attempted by using the selected demand-dial interface when a Domain Name System (DNS) name resolution request is received by a host on the private network.


Specifies that this interface is a private interface that is connected to the private network.


Specifies that this interface is the public interface that is connected to the Internet.


Specifies whether the router performs TCP port and UDP port translation in addition to IP address translation. If you only have a single public IP address, you must select this check box. Otherwise, network traffic from hosts on the private network cannot be properly translated to Internet traffic.


Lists the configured ranges of public IP addresses assigned to you. The address ranges are typically obtained from your Internet service provider.


Click to add a public address range to the list.


Click to modify a selected public address range on the list.


Removes a selected public address range from the list.


Click to reserve specific public IP addresses from the configured ranges that cannot be used for address translation. Reserved public IP addresses can be used for Internet Web servers that are placed on the private network. You cannot configure a reservation until you configure at least one IP address pool.


Provides a space for you to type the IP address (in dotted decimal notation) of the starting number of your public address pool.


Provides a space for you to type the IP address (in dotted decimal notation) of the ending number of your public address pool.


Provides a space for you to type the subnet mask (in dotted decimal notation) for your public address pool.


Lists the configured reservations. Each reservation maps a specific public IP address from the public address pool to a specific private address. Reserved public IP addresses are not used for dynamically mapped traffic.


Click to add a reservation.


Click to modify the selected reservation.


Removes the selected reservation.


Specifies whether sessions from the public network are allowed. If you are setting up a server, such as a Web server, and you want to make it accessible for Internet users, select this check box. Normally, the only traffic that is allowed from the public network is traffic sent in response to sessions initiated from the private network.


Provides a space for you to type the IP address in the public address pool that is being reserved.


Provides a space for you to type the IP address of the private network computer that you want to make available to public network users.


Lists the protocols for which you can configure special ports (TCP and UDP).


Lists the configured special ports.


Click to add a special port.


Click to modify the selected special port.


Removes the selected special port.


Specifies that the incoming IP address is the public IP address that is assigned to this interface.


Specifies that the incoming IP address is from the public address pool.


Provides a space for you to type the destination port number of the private traffic. For example, for a Web server on your private network, the outgoing port number is 80.


Provides a space for you to type the destination port number of incoming public traffic. For example, for a Web server on your private network, the incoming port number is 80.


Provides a space for you to type the IP address (in dotted decimal notation) for the private network computer.


Provides a space for you to type the appropriate public IP address (in dotted decimal notation) from the public address pool.


Specifies that no IPX events are logged in the System Log in Event Viewer.


Specifies that only IPX errors are logged in the System Log in Event Viewer.


Specifies that IPX errors and warnings are logged in the System Log in Event Viewer.


Specifies that the maximum amount of IPX information is logged in the System Log in Event Viewer.


Specifies whether the IPX protocol is enabled on this interface.


The dial-in control protocol is the protocol that is used to establish a dial-up connection. The configuration of the dial-in control protocol is only available for demand-dial interfaces.


Specifies that IPX Control Protocol (CP) is used to establish a dial-up connection that is based on the Point-to-Point Protocol (PPP). You should select this option if your routers are using Windows 2000. IPX CP is also supported for dial-up clients.


Specifies that the IPX WAN control protocol is used to establish a demand-dial connection. You should select this option if your routers are using Novell NetWare remote access software. IPX WAN is not supported for dial-up clients.


Click to apply packet filters to incoming IPX packets on this interface.


Click to apply packet filters to outgoing IPX packets on this interface.


Provides a space for you to type the IPX internal network number. By default, a unique IPX internal network number is dynamically assigned when the router is started for the first time.


For input filters: Specifies that all incoming packets that match the filters listed are discarded. All incoming packets are compared to the filters listed. If a packet matches a filter, the packet is dropped. If the packet does not match a filter, the packet is accepted.

For output filters: Specifies that all outgoing packets that match the filters listed are discarded. All outgoing packets are compared to the filters listed. If a packet matches a filter, the packet is dropped. If the packet does not match a filter, the packet is transmitted.

This option applies to all the filters that you added. You cannot change this option for individual filters.

You can only configure the filter action after you add at least one filter.


For input filters: Specifies that all incoming packets that match the filters listed are accepted. All incoming packets are compared to the filters listed. If a packet matches a filter, the packet is accepted. If the packet does not match a filter, the packet is dropped.

For output filters: Specifies that all outgoing packets that match the filters listed are transmitted. All outgoing packets are compared to the filters listed. If a packet matches a filter, the packet is transmitted. If the packet does not match a filter, the packet is dropped.

This option applies to all the filters that you added. You cannot change this option for individual filters.

You can only configure the filter action after you add at least one filter.


Lists all the configured filters.


Click to add a filter. You can set filters based on where the packet is coming from (the source), where the packet is going (the destination), or the type of packet to use. You can set all three of these options for a filter or any one or combination of the three, depending on the level of control that you want.


Click to modify the settings for a selected filter.


Deletes a selected filter from the list.


Provides a space for you to type the 4-byte network number in hexadecimal format (8 hexadecimal digits) that is used to uniquely identify the network from which the packet was sent. You must also specify a network mask.


Provides a space for you to type a 4-byte mask in hexadecimal format (8 hexadecimal digits) that is used to identify a range of IPX network numbers. To determine whether the source network number of an IPX packet matches the filter, the router performs a bitwise logical AND of the source network mask and the source network number in the IPX packet and compares the result to the source network number of the filter. You can use "0" as a wildcard character for any hexadecimal digit and "F" for a specific hexadecimal digit.


Provides a space for you to type the 6-byte node address in hexadecimal format (12 hexadecimal digits) that is used to store the IEEE-administered physical or hardware address assigned to the network adapter of the node. The source node is an optional filter value.


Provides a space for you to type the 2-byte socket number in hexadecimal format (4 hexadecimal digits) that identifies the individual software or client process that is communicating. You can use socket numbers to send and receive packets to the proper process.


Provides a space for you to type the 4-byte network number in hexadecimal format (8 hexadecimal digits) that is used to uniquely identify the network to which the packet is going. You must also specify a network mask.


Provides a space for you to type a 4-byte mask in hexadecimal format (8 hexadecimal digits) that is used to identify a range of IPX network numbers. To determine whether the destination network number of an IPX packet matches the filter, the router performs a bitwise logical AND of the destination network mask and the destination network number in the IPX packet and compares the result to the destination network number of the filter. You can use "0" as a wildcard character for any hexadecimal digit and "F" for a specific hexadecimal digit.


Provides a space for you to type the 6-byte node address in hexadecimal format (12 hexadecimal digits) that is used to store the IEEE-administered physical or hardware address assigned to the network adapter of the node. The source node is an optional filter value.


Provides a space for you to type the 2-byte socket number in hexadecimal format (4 hexadecimal digits) that identifies the individual software or client process that is communicating. You can use socket numbers to send and receive packets to the proper process.


Provides a space for you to type the 1-byte packet type number in hexadecimal format (2 hexadecimal digits) that identifies the type of IPX packet.


Specifies whether NetBIOS broadcasts are accepted on this interface.


Specifies that NetBIOS broadcasts are always delivered to all interfaces except the interface on which the NetBIOS over IPX broadcast was received. An exception is if the NetBIOS over IPX broadcast has already been on the IPX network to which the outgoing interface is attached.

If this option is enabled for a demand-dial interface, the demand-dial connection is established whenever a Windows 2000-based router receives a NetBIOS-over-IPX broadcast.


Specifies that NetBIOS broadcasts are never delivered on this interface. With this setting, Windows 2000-based routers silently discard NetBIOS broadcasts. This is the default setting for demand-dial interfaces.


Specifies that only NetBIOS broadcasts that are defined for statically configured names are delivered. These names are configured in the Static NetBIOS Name dialog box.


Specifies that NetBIOS broadcasts are delivered if an interface is up. This option is designed for demand-dial interfaces. If the interface is not up (in a connected state), the router does not bring up the interface to deliver the broadcast.


Provides a space for you to type a 4-byte IPX network number in hexadecimal format (8 hexadecimal digits).


Provides a space for you to type the 6-byte media access control (MAC) address in hexadecimal format (12 hexadecimal digits) of the next-hop router interface that is used to reach the network defined in Network Number.


Provides a space for you to type the number of ticks (1/18 second) it takes a packet to reach the network. You can also click the arrows to select a new setting.


Provides a space for you to type the number of routers to cross (hops) to reach the network. You can also click the arrows to select a new setting. IPX networks with a hop count greater than 16 hops are considered unreachable.


Lists the available IPX interfaces on the router. Select the interface over which the IPX network defined in Network Number is reachable.


Provides a space for you to type a 2-byte service type in hexadecimal format (4 hexadecimal digits).


Provides a space for you to type the name of the service that can be reached through this interface. The SAP service name can be up to 48 bytes long. Names under 48 bytes are terminated with a null character (ASCII NUL) in the Server Name field in the SAP header.


Provides a space for you to type the 4-byte IPX network number in hexadecimal format (8 hexadecimal digits).


Provides a space for you to type the 6-byte IPX node address in hexadecimal format (12 hexadecimal digits).


Provides a space for you to type the 2-byte IPX socket number in hexadecimal format (4 hexadecimal digits).


Provides a space for you to type the number of routers to cross (the number of hops) to reach the service. You can also click the arrows to select a new setting. Services with a hop count greater than 16 hops are considered unreachable.


Lists the available IPX interfaces on the router. Select the interface over which the service is reachable.


Provides a space for you to type the first 15 characters of the NetBIOS service name. For computers running Windows 2000, this usually corresponds to the computer name. For example, you use the name of your computer with the net use command.


Provides a space for you to type the last byte of the NetBIOS name in hexadecimal format (2 hexadecimal digits). This is the last byte of the full 16-character NetBIOS name, which is typically used to indicate the type of NetBIOS process. If you are not sure what the number is, leave this option blank.


Lists the available IPX interfaces on the router. Select the interface over which the NetBIOS name query broadcast for this name is forwarded.


Specifies that no RIP-for-IPX events are logged in the System Log in Event Viewer.


Specifies that only RIP-for-IPX errors are logged in the System Log in Event Viewer.


Specifies that RIP-for-IPX errors and warnings are logged in the System Log in Event Viewer.


Specifies that the maximum amount of RIP-for-IPX information is logged in the System Log in Event Viewer.


Specifies whether RIP for IPX is enabled on this interface.


Specifies whether RIP for IPX advertises routes on this interface. By default, this check box is selected.


Specifies whether RIP for IPX accepts route advertisements from other routers over this interface. By default, this check box is selected.


Specifies that routes are periodically advertised according to the value in Update Interval. This is the default for LAN interfaces.


Specifies that routes are never updated on this interface.


Specifies that this interface performs routing updates only through static updates across demand-dial connections. This is the default for demand-dial interfaces.


Provides a space for you to type the update interval (in seconds) that specifies how often routes are advertised on this interface. The default update interval is 60 seconds.


Provides a space for you to type the aging interval multiplier. This number (for example, 3) is multiplied by the number in Update Interval (for example, 60) to calculate the total number of seconds that learned routes are considered valid before they are removed from the IPX routing table (for example, 180 seconds).


Click to apply RIP route filters to incoming RIP-for-IPX route advertisements on this interface.


Click to apply RIP route filters to outgoing RIP-for-IPX route advertisements on this interface.


For input filters: Specifies that the listed routes are ignored when received in a RIP-for-IPX advertisement. All routes are compared to the filters listed. If a route matches a filter, the route is ignored. If the route does not match a filter, the route is accepted.

For output filters: Specifies that the listed routes are not advertised in RIP-for-IPX advertisements sent by this router. All routes are compared to the filters listed. If a route matches a filter, the route is not advertised. If the route does not match a filter, the route is advertised.

This option applies to all the filters that you added. You cannot change this option for individual filters.

You can only configure the filter action after you add at least one filter.


For input filters: Specifies that the listed routes are accepted when received in a RIP-for-IPX advertisement. All incoming routes are compared to the filters listed. If a route matches a filter, the route is accepted. If the route does not match a filter, the route is ignored.

For output filters: Specifies that the listed routes are advertised in RIP-for-IPX advertisements sent by this router. All outgoing routes are compared to the filters listed. If a route matches a filter, the route is advertised. If the route does not match a filter, the route is not advertised.

This option applies to all the filters that you added. You cannot change this option for individual filters.

You can only configure the filter action after you add at least one filter.


For input filters: Lists the routes to either ignore or accept when received in a RIP-for-IPX router advertisement.

For output filters: Lists the routes to either advertise or not advertise in RIP-for-IPX router advertisements sent by this router.


Click to add a route.


Click to modify a selected route.


Deletes a selected route.


Displays the interface on which RIP route filtering is being configured.


Displays the interface on which RIP route filtering is being configured.


Provides a space for you to type a 4-byte number in hexadecimal format (8 hexadecimal digits) that identifies the IPX network.


Provides a space for you to type a 4-byte mask in hexadecimal format (8 hexadecimal digits) that is used to identify a range of IPX network numbers. To determine whether the incoming or outgoing route matches the filter, the router does a bitwise logical AND of the network mask and the network number of the route and compares the result to the specified network number. You can use "0" as a wildcard character for any hexadecimal digit and "F" for a specific hexadecimal digit.


Specifies that no SAP-for-IPX events are logged in the System Log in Event Viewer.


Specifies that only SAP-for-IPX errors are logged in the System Log in Event Viewer.


Specifies that SAP-for-IPX errors and warnings are logged in the System Log in Event Viewer.


Specifies that the maximum amount of SAP-for-IPX information is logged in the System Log in Event Viewer.


Specifies whether SAP for IPX is enabled on this interface.


Specifies whether SAP services are advertised on this interface. By default, this check box is selected.


Specifies whether SAP service advertisements that come from other routers are accepted over this interface. By default, this check box is selected.


Specifies whether SAP GetNearestServer requests from IPX nodes are replied to on this interface. By default, this check box is selected.

The SAP GetNearestServer request is sent out by IPX nodes that attempt to locate the "nearest" server of a specific service type on the network. Nearest is defined as the SAP agent that is able to respond the quickest. For example, a NetWare client attempts to find the nearest NetWare server on the IPX internetwork for login purposes.


Specifies that SAP services are periodically advertised according to the value in Update Interval. This is the default for LAN interfaces.


Specifies that SAP services are never updated on this interface.


Specifies that this interface can perform SAP service updates only through static updates across demand-dial connections. This is the default for demand-dial interfaces.


Specifies and provides a space for you to type how often (in seconds) SAP services are advertised on this interface. The default update interval is 60 seconds.


Provides a space for you to type the aging interval multiplier. This number (for example, 3) is multiplied by the number in Update Interval (for example, 60) to calculate the total number of seconds that learned SAP services are considered valid before they are removed from the IPX service table (for example, 180 seconds).


Click to apply SAP service filters to incoming SAP-for-IPX service advertisements on this interface.


Click to apply SAP service filters to outgoing SAP-for-IPX service advertisements on this interface.


For input filters: Specifies that the listed services are ignored when received in a SAP-for-IPX advertisement. All services are compared to the filters listed. If a service matches a filter, the service is ignored. If the service does not match a filter, the service is accepted.

For output filters: Specifies that the listed services are not advertised in-SAP for-IPX advertisements sent by this router. All services are compared to the filters listed. If a service matches a filter, the service is not advertised. If the service does not match a filter, the service is advertised.

This option applies to all the filters that you added. You cannot change this option for individual filters.

You can only configure the filter action after you add at least one filter.


For input filters: Specifies that the listed services are accepted when received in a SAP-for-IPX advertisement. All incoming services are compared to the filters listed. If a service matches a filter, the service is accepted. If the service does not match a filter, the service is ignored.

For output filters: Specifies that the listed services are advertised in SAP-for-IPX advertisements sent by this router. All outgoing services are compared to the filters listed. If a service matches a filter, the service is advertised. If the service does not match a filter, the service is not advertised.

This option applies to all the filters that you added. You cannot change this option for individual filters.

You can only configure the filter action after you add at least one filter.


For input filters: Lists the services to either ignore or accept when received in a SAP-for-IPX advertisement.

For output filters: Lists the services to either advertise or not advertise in SAP-for-IPX advertisements sent by this router.


Click to add a service.


Click to modify a selected service.


Deletes a selected service.


Displays the interface on which SAP service filtering is being configured.


Displays the interface on which SAP service filtering is being configured.


Provides a space for you to type a 2-byte service type in hexadecimal format (4 hexadecimal digits). You can use a service type of "FFFF" to indicate all service types.


Provides a space for you to type the name of the service. This is typically the name of the server hosting the service, which can be up to 48 bytes long. You can use a service name of "*" to indicate all service names. You cannot use the asterisk wildcard character (*)within a service name.


Sets the column display to the default columns and order.


Moves the selected column heading up in the list under Columns.


Moves the selected column heading down in the list under Columns.


Lists the column headings. To add a column heading to the Routing and Remote Access window, select the appropriate check box. To remove a column heading from the Routing and Remote Access window, clear the appropriate check box. To revert back to the default column headings, click Use Defaults.